Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | MiroContentLogsDataConnector |
| Publisher | Miro |
| Used in Solutions | Miro |
| Collection Method | CCF |
| Connector Definition Files | MiroContentLogs_DataConnectorDefinition.json |
| DCR Definition Files | MiroContentLogs_DCR.json |
| CCF Configuration | MiroContentLogs_PollingConfig.json |
| CCF Capabilities | APIKey, Paging |
The Miro Content Logs data connector enables you to ingest content activity logs from Miro into Microsoft Sentinel. Part of Miro's Enterprise Guard eDiscovery capabilities, this connector provides content-level visibility for compliance, legal hold, and advanced threat detection.
Key features:
Track all content item changes.
Monitor content modifications by user and timestamp.
Support compliance and eDiscovery requirements.
Detect data exfiltration and insider threats.
Meet regulatory and legal hold obligations.
Requirements:
Miro Plan: Enterprise Plan + Enterprise Guard add-on.
OAuth scope: contentlogs:export.
Role: Company Admin in your Miro organization.
Organization ID: Your Miro organization identifier.
💡 Not on Enterprise Plan yet? Upgrade to Miro Enterprise to unlock advanced security and compliance features for your team's collaboration activities in Microsoft Sentinel.
💡 Need Content Logs? Content activity logging is part of Miro Enterprise Guard, which provides advanced security, compliance, and eDiscovery features. Contact your Miro account manager to add Enterprise Guard to your Enterprise Plan and unlock content-level monitoring in Microsoft Sentinel.
Note: If you only have the base Enterprise Plan (without Enterprise Guard), please use the Miro Audit Logs connector instead for organization-level event monitoring.
For detailed instructions, refer to the documentation.
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
MiroContentLogs_CL |
? | ✓ | ? |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Resource Provider Permissions:
Custom Permissions:
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
Step 1: Verify your Miro plan and Enterprise Guard
Step 2: Choose your setup option
There are two ways to set up the Miro Content Logs connector.
Option 1 (recommended): Use Enterprise integrations
Option 2 (alternative): Create custom OAuth application
Note: When using Option 1, the integration is automatically tied to the team with the largest number of users in your organization. When using Option 2, you can choose which team to install the app to. However, the team selection does not affect which logs are collected—both options provide organization-wide log access. All integration-relevant events from all teams are included in your logs.
Option 1: Enterprise integrations (recommended)
https://miro.com/app/settings/company/{ORGANIZATION_ID}/.Option 2: Custom OAuth application (alternative)
contentlogs:export.https://miro.com/app/settings/company/{ORGANIZATION_ID}/.Step 3: Learn more
For detailed information about Miro content logs and eDiscovery:
6. Connect to Miro to start collecting content logs in Microsoft Sentinel.
Step 4: Connect to Miro
Provide the required values below to complete the connection.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊